Skip to content

fix: ensure plugin version is updated in action.yml #1257

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

algomaster99
Copy link
Member

The $PLUGIN_VERSION is pinned to 5.5.2. It was accidentally introduced in https://github.com/chains-project/maven-lockfile/pull/1211/files#diff-e23072be6fce0672ff37f9bae970d4df7189edd43bccee7223ae0b0c25b090f5R95. These changes ensure that action.yml is updated accordingly with each release.

@algomaster99 algomaster99 requested a review from LogFlames June 24, 2025 16:32
@algomaster99
Copy link
Member Author

@LogFlames please review this small PR. Once you merge, I suggest that you make a patch release because maven-lockfile-github-action:5.6.0 still invokes 5.5.2.

@algomaster99 algomaster99 changed the title fix: ensure plugin version is updated fix: ensure plugin version is updated in action.yml Jun 24, 2025
@LogFlames
Copy link
Member

Thanks for the PR!

Unfortunately I haven't gotten SNAPSHOT releases to work yet, so this would cause CI to fail as the latest SNAPSHOT version of maven-lockfile is not available on maven central.

I'm also thinking that it might be preferable for the project to use the latest full release of the project:

  • Do you know if the doc generation can get that, or if we should use a curl/grep similar to how Spoon calculates the name of the next beta release?
  • Do you think this makes sense, or would the latest -SNAPSHOT be preferable?

@algomaster99
Copy link
Member Author

I'm also thinking that it might be preferable for the project to use the latest full release of the project:

I agree with this.

Do you know if the doc generation can get that

Yes, if you can have a script to get the version from POM and then trigger this script only on ReleaseEvent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants